5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
- Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-16: Using GUI Features of the Image Editor

Image Field Control Options


Note that available options differ depending on the control type selected.

Prompt indicates the text to appear as the label appropriate for this design control type. For example, at the frame level this would be titlebar text. At the button level, it would be button label text. For an optional child, it is the text that appears on the menu but if left blank, the processes' descriptive name is used.

Text Position indicates where the text should appear inside the button. Click the list button for a drop-down list of selections that include: CENTER, TOP, RIGHT, BOTTOM, LEFT, UPPER RIGHT, UPPER LEFT, LOWER RIGHT and LOWER LEFT.

Resource specifies the application and name of a resource defined in Named Resources which links to one or more graphics files. Different graphics can apply depending upon resource state (disabled, enabled, rollover, pressed, etc). Select the scan icon for a list of available resources.

Icon Position indicates where the defined icon (if any) should be placed in relation to the field contents. Click the list button for a drop-down list of selections that include BEHIND TEXT, ABOVE TEXT, TRAILING TEXT, BELOW TEXT, LEADING TEXT, ABOVE & TRAILING, ABOVE & LEADING, BELOW & TRAILING, BELOW & LEADING, EXPAND TO FILL, and EXPAND PROP'L.

Picture Loc indicates the location of the graphic to be used. Click the list button for a list of available locations that include: CLIENT URL, CLIENT FILE, DIRECT, SERVER URL, SERVER FILE, and DESIGN FILE.

Transparent Background? indicates whether or not this field should have a transparent background. Select 'yes' or 'no' .

Option indicates the option number, if any, to be sent to the server by the client whenever the contents of this field are changed. This is useful in situations where you want other changes made to the screen based on the contents of this field. Click the list button for a list of available options.

Tooltip is 60 characters of help text that you can enter. The tooltip is displayed to users as a "hover over" when the mouse pointer is passed over the respective icon.

Tab In  --- OPTION will be set to TAB IN and --- CURSOR AT FIELD will contain the name of the field the user tabbed into. 

Tab Out --- OPTION will be set to TAB OUT and --- CURSOR AT FIELD will be set to the field they tabbed out of.  If the field value changed, then --- OPTION will be set to VALUE CHANGED and ---- CURSOR AT FIELD will contain the name of the field that was changed.

The Value Changed event will be triggered under 2 circumstances:

if the user changes the field and Tabs out (either manually or via auto tab). If the field also has Tab Out checked, then 2 events will fire, first the VALUE CHANGED event will fire, then the TAB OUT event will fire. If the next field has Tab In checked, then a third event will fire, TAB IN for the next field.
if the user changes the field but does not leave the field before valueChangedTimer (in Client Preferences) has expired. For example, if valueChangedTimer is set to 300 ms and the user changes the value in the field, but does not exit the field before 300 ms have passed since they started typing in the field, the VALUE CHANGED event will fire. The timer will reset and will fire again if the user continues to change the field but does not exit before the valueChangedTimer has expired again. If the user does not make any further changes since the last time VALUE CHANGED fired and simply tabs out of the field, the event will not fire again, as they did not change the field since the last time the event fired.

If you have Tab Out set on one field and Tab In set on the next field, then the Option Intercept Event Point will fire twice, once when they tab out of the first field (with OPTION set to TAB OUT and CURSOR AT FIELD set to the first field, then immediately afterwards with OPTION set to TAB IN and CURSOR AT FIELD set to next field).

Since these attributes use --- CURSOR AT FIELD to tell you which field was affected, you can only set these attributes where there is an actual underlying data field. For example, buttons, labels, boxes, etc, do not have these event types.

Application Design Manual                                         "Powered by Appx Software"

1306

©2006 By APPX Software, Inc. All Rights Reserved